I'm working redoing the K2CNC code and they auto-start with thread 6 then jump to thread 1 for monitoring limits. I want to start with Thread 1 then jump to Thread 2 for monitoring limits. Is there any reason or preference using one Thread over another?

The manual states Thread #7 continues to run after Stop.

Does thread #7 start at power up or after loading SW?

If it doesn't start at power up do you need to start the thread? via Execute<N>

If nothing is loaded in Thread #7 is it part of the total executing time show on page 195, which doesn't show Thread #7 in the example, only Threads 0-2.

Thanks, Eric.

Hi Eric,

Actually Thread #1 (not 7) is not killed by EStop in KMotionCNC.

Thread #7 has more memory space than the others (5x64KBytes vs 64KBytes)

Other than that the Threads are identical.

If you use Thread#2 for watching limits make sure no other Program is loaded into Thread #2 by other MCode Actions or User Buttons.

Flashing the "Launch on Power Up" options define which Threads start on KFLOP Power up. 

CPU time is only allocated for active Threads.  A Thread only uses CPU cycles while it is executing and hasn't been halted or terminated.

HTH

Regards

TK

 

I'm working redoing the K2CNC code and they auto-start with thread 6 then jump to thread 1 for monitoring limits. I want to start with Thread 1 then jump to Thread 2 for monitoring limits. Is there any reason or preference using one Thread over another?

The manual states Thread #7 continues to run after Stop.

Does thread #7 start at power up or after loading SW?

If it doesn't start at power up do you need to start the thread? via Execute<N>

If nothing is loaded in Thread #7 is it part of the total executing time show on page 195, which doesn't show Thread #7 in the example, only Threads 0-2.

Thanks, Eric.